home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Technotools
/
Technotools (Chestnut CD-ROM)(1993).ISO
/
lang_c
/
msc4add
/
insert.doc
next >
Wrap
Text File
|
1987-01-24
|
2KB
|
50 lines
Documentation for INSERT, etc.
Files in INSERT.ARC:
INSERT.DOC - this document
INSERT.TXT - ascii version of INSERT
INSERT.WP - WordPerfect-format version
INSERT.WS - WordStar-format version
The manual for Microsoft C version 4.0 contains a chapter (part 1, ch. 4),
entitled "Run-Time Routines by Category. This summary is a very useful
addition to the main (alphabetical) reference section (part 2), but I wish more
attention had been given to its organization and contents.
INSERT is a 5-page (manual-size) summary of information on file-associated
functions and string/buffer manipulation functions which I refer to in
preference to Microsoft's summary. I inserted these pages after page 88 in my
manual. They have page numbers 88-a through 88-e included in the text.
To Print:
This insert is intended to be printed at 6 lines-per-inch and (about) 15-pitch,
with the printer set to begin printing 1/2 inch from the top of the sheet
(physical line 4) and at the left edge of the sheet (1st position after the
perf). Cut-lines are included in the text. The .TXT version can be simply
COPYd to PRN after setting up your printer this way. You may prefer to read
the next paragraphs, however.
I like to underline the category headings and bold-print the function names.
The .WP and .WS versions include underlining and bold-printing, as well as
margin settings. The .WP version also includes a 15-pitch setting. Both
assume tabs are set every 5 spaces.
To use the .WS version, you will have to take care of pitch-setting yourself.
If you use another word processor, you may wish to edit the .TXT version to add
underlining and bold-printing.
Some notes on the information organization:
The i/o routines and the string routines are organized differently because I
find that I have different requirements when I need to refer to these 2 groups
of functions. When I need to consult the former, I normally need to refresh my
memory about function names, argument requirements, error-conditions, and
include-file requirements -- I generally know the functional behavior. For
string/buffer routines, I usually need to compare functional differences to
decide among several ways to approach a string manipulation operation.